Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSockets Next: add integration test module #44442

Merged
merged 1 commit into from
Nov 13, 2024
Merged

Conversation

mkouba
Copy link
Contributor

@mkouba mkouba commented Nov 12, 2024

- add this module in the native-tests.json config in the HTTP category
- fixes quarkusio#44434
@mkouba mkouba requested a review from gsmet November 12, 2024 12:25
@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label Nov 12, 2024
@mkouba mkouba added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Nov 12, 2024
Copy link

quarkus-bot bot commented Nov 12, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 3c955f4.

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
✔️ JVM Tests - JDK 17 Logs Raw logs 🔍
✔️ JVM Tests - JDK 21 Logs Raw logs 🔍
JVM Tests - JDK 17 Windows Build Failures Logs Raw logs 🔍

Full information is available in the Build summary check run.
You can consult the Develocity build scans.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: integration-tests/grpc-descriptor-sets/grpc-descriptor-set-alternate-output-dir 

📦 integration-tests/grpc-descriptor-sets/grpc-descriptor-set-alternate-output-dir

io.quarkus.grpc.examples.hello.DescriptorSetExistsTest.descriptorSetExists line 16 - History - More details - Source on GitHub

java.lang.AssertionError: 

Expecting path:
  D:\a\quarkus\quarkus\integration-tests\grpc-descriptor-sets\grpc-descriptor-set-alternate-output-dir\target\proto
to exist (symbolic links were followed).
	at io.quarkus.grpc.examples.hello.DescriptorSetExistsTest.descriptorSetExists(DescriptorSetExistsTest.java:16)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 integration-tests/opentelemetry-vertx-exporter

io.quarkus.it.opentelemetry.vertx.exporter.grpc.SimpleGrpcWithTLSNoCompressionTest.test - History

  • No value present - java.util.NoSuchElementException
java.util.NoSuchElementException: No value present
	at java.base/java.util.Optional.get(Optional.java:143)
	at io.quarkus.it.opentelemetry.vertx.exporter.AbstractExporterTest.getMetric(AbstractExporterTest.java:145)
	at io.quarkus.it.opentelemetry.vertx.exporter.AbstractExporterTest.verifyMetrics(AbstractExporterTest.java:101)
	at io.quarkus.it.opentelemetry.vertx.exporter.AbstractExporterTest.test(AbstractExporterTest.java:53)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at io.quarkus.test.junit.QuarkusTestExtension.runExtensionMethod(QuarkusTestExtension.java:966)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestMethod(QuarkusTestExtension.java:816)

@mkouba
Copy link
Contributor Author

mkouba commented Nov 13, 2024

The io.quarkus.grpc.examples.hello.DescriptorSetExistsTest.descriptorSetExists failure does not seem to be related. Do you happen to know if it's a new flaky test? @gsmet

@gsmet
Copy link
Member

gsmet commented Nov 13, 2024

@mkouba you can check the history with the History link at the right of the test name. It poins to the Develocity UI. From what I can see, it looks like it has failed before.

@gsmet gsmet merged commit 323ba29 into quarkusio:main Nov 13, 2024
52 of 53 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.17 - main milestone Nov 13, 2024
@quarkus-bot quarkus-bot bot added kind/enhancement New feature or request and removed triage/waiting-for-ci Ready to merge when CI successfully finishes labels Nov 13, 2024
@mkouba
Copy link
Contributor Author

mkouba commented Nov 13, 2024

@mkouba you can check the history with the History link at the right of the test name. It poins to the Develocity UI. From what I can see, it looks like it has failed before.

Ah, ok. Why is it listed in Failures and not Flaky tests then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure kind/enhancement New feature or request triage/flaky-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebSockets Next: add integration test module
2 participants